fix: forward Lua version features from selene-lib to CLI crate - #666

I noticed a weird subtlety related to this.

I've sent this PR #646 which fixed the problem for me (the propagation of lua version). However, I now stumbled upon your change and I started wondering why did my change fix the problem for me, when your change looks like it should be required too.

Well, I was building my selene binary with cargo build --release and not with cargo install selene (or running cargo run -p selene). If building selene with cargo build it seems like the defaults are picked for the full workspace which then sets more defaults than the selene/Cargo.toml.

I verified this theory with the below repros:

 # selene.toml
std = "lua53"

-- test.lua
local x = 1 & 2

running cargo run -p selene -- --config selene.toml test.lua fails with

ERROR: lua version lua53 in standard library, but feature for it is not enabled
ERROR: lua version lua52 in standard library, but feature for it is not enabled
error[parse_error]: unexpected character &
  ┌─ test.lua:1:13
  │
1 │ local x = 1 & 2
  │             ^

error[parse_error]: unexpected token `2`
  ┌─ test.lua:1:15
  │
1 │ local x = 1 & 2
  │               ^ unexpected token, this needs to be a statement

but it works fine if I instead do:

cargo build --release
../target/release/selene --config selene.toml test.lua

So IMO both PRs are needed. Mine fixes Lua version inheritance in config files and yours adds the right build time feature enables.